home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr28
/
doc_proc.zip
/
SAMP-DOC.ZIP
/
RELEASE.DOC
< prev
next >
Wrap
Text File
|
1992-11-08
|
8KB
|
94 lines
*************************************
* *
* R E L E A S E *
* ON THE MVS/XA OPERATING SYSTEM *
* *
*************************************
John S. Ward
04/15/93
EJECT
The RELEASE procedure collects unused disk space from user's data
sets and makes it available to the system. This unused space is
generated when you allocate a data set that is larger than you need at
the present. For a partitioned data set, a new copy of a member is
made every time you update that member and save it. Therefore, all the
previous copies of that member gradually fill the extra space. For
this reason, you must periodically compress your data set in order to
delete the earlier copies. Compressing a data set, however, only frees
the space from the unwanted copies, and releases it back to the data
set itself. It does not allow the system to take over this extra space
for other use.
On the other hand, The RELEASE procedure first compresses all
partitioned data sets in order to identify the true space used. Next,
it releases the unused spaces from all data sets under a user-id, back
to the system. This does not mean that you cannot ask for more space.
Space is dynamically allocated as needed.
To release maximum space, go to COMMAND PROCESSOR PANEL (OPTION 6),
and enter %RELEASE. (Or enter TSO %RELEASE from any panel's main
command line.)
It may take anywhere from thirty seconds to two minutes for this
program to complete execution. Any data sets that are currently
allocated to your terminal are not included in the release process.
Additionally, you should not execute %RELEASE at the same time you
are running a batch job. %RELEASE needs to have exclusive use of
the data sets and will have to wait if a batch job has one of your
data sets.
NOTE: The RELEASE procedure releases the unused space from the primary
allocation, as well as the secondary extents. The secondary
extents are given back as needed, but the unused space from the
primary allocation is lost. Therefore, it is recommended to
create data sets that have a small primary allocation, and a
larger secondary extends.